Skip to main content

Essential Git Commands: A Beginner's Guide to Version Control

Git Commands Guide

This article offers a quick overview of essential Git commands, organized for easy access.

Getting Started

  1. Initialize Repository: git init - Start a new Git repository in the current directory.
  2. Clone Repository: git clone [URL] - Download an existing repository from a remote source.

Working with Remotes

  1. List Remotes: git remote -v - View all remote connections.
  2. Add Remote: git remote add [name] [URL] - Connect a new remote repository.
  3. Remove Remote: git remote rm [name] - Delete a remote connection.
  4. Fetch Remote Changes: git fetch [remote] - Download updates without merging.
  5. Pull Changes: git pull [remote] [branch] - Fetch and merge changes from a remote branch.
  6. Push Changes: git push [remote] [branch] - Upload changes to a remote branch.

Branching & Merging

  1. List Branches: git branch - See all branches in the repository.
  2. Create Branch: git branch [name] - Make a new branch.
  3. Switch Branch: git checkout [name] - Move to an existing branch.
  4. Create & Switch Branch: git checkout -b [name] - Create and switch to a new branch simultaneously.
  5. Merge Branch: git merge [branch] - Combine changes from one branch into the current branch.
  6. Delete Branch: git branch -d [name] - Remove a branch that has been merged.

Making Changes

  1. Status: git status - Show the current status of the working directory and staging area.
  2. Add Changes: git add [file/directory] - Stage changes for the next commit.
  3. Commit Changes: git commit -m "[message]" - Save changes with a descriptive message.
  4. Amend Commit: git commit --amend - Edit the most recent commit.
  5. Reset: git reset [file] - Unstage changes while keeping them in the working directory.
  6. Hard Reset: git reset --hard [commit] - Reset the current branch to a specific commit, discarding all changes.

Reviewing History

  1. Log: git log - Display a list of past commits.
  2. Log (Graph): git log --graph - View commit history as a graph.
  3. Show Change: git show [commit] - Show details of a specific commit.
  4. Diff: git diff [branch] - Compare changes between branches or commits.

Cleanup & Maintenance

  1. Stash Changes: git stash - Temporarily save changes without committing.
  2. Apply Stash: git stash pop - Retrieve stashed changes.
  3. Clean Untracked Files: git clean -f - Remove files not tracked by Git.

Advanced & Miscellaneous

  1. Rebase: git rebase [branch] - Reapply commits on top of another base commit.
  2. Cherry-pick: git cherry-pick [commit] - Apply a specific commit from one branch onto another.
  3. Tag: git tag [name] - Create a tag for marking specific points in the commit history.
  4. Search Log: git log --grep="[pattern]" - Search commit messages for a pattern.

Comments

Popular posts from this blog

A Complete CI/CD Pipeline

Complete CI/CD Pipeline Using GitHub, Jenkins, Maven, SonarQube, Nexus, and Docker A well-designed CI/CD pipeline plays a critical role in modern DevOps practices by automating software delivery, improving code quality, and reducing deployment risks. In this article, I will explain how I build an automated CI/CD pipeline using GitHub, Jenkins, Maven, SonarQube, Nexus Repository, Docker, and Docker Hub. Source Code Management with GitHub The CI/CD workflow begins with storing the application source code in GitHub. Developers regularly push code changes or create pull requests to collaborate on features and bug fixes. Whenever new code is pushed to the repository, GitHub triggers Jenkins automatically through a webhook. This integration helps start the CI/CD pipeline without manual intervention. Code Checkout Stage in Jenkins The first stage of the pipeline is the checkout process. Jenkins connects to the GitHub repository and pulls the latest version of the source code. ...

Terraform for AWS: Step-by-Step Infrastructure Automation That Actually Works

How I Use Terraform to Provision and Manage AWS Infrastructure Efficiently Infrastructure as Code (IaC) has become a critical part of modern cloud operations, and Terraform is one of the most popular tools for automating cloud infrastructure deployment. In this article, I'll share how I use Terraform to build and manage AWS resources such as Virtual Private Clouds (VPCs), EC2 instances, Application Load Balancers (ALBs), and Auto Scaling Groups. Building AWS Infrastructure with Terraform My infrastructure deployment process begins by defining all AWS resources as code. This approach ensures consistency, repeatability, and easier management across multiple environments. The first step is creating a secure network architecture using a VPC. Within the VPC, I configure public and private subnets, route tables, internet gateways, and other networking components required for application deployment. Once the networking layer is ready, I deploy EC2 instances inside private su...

Master Linux Administration for DevOps: Powerful Commands, Troubleshooting Tips & Best Practices

Linux administration is one of the most important skills for anyone working in DevOps. From application servers and CI/CD platforms to containers and cloud infrastructure, Linux-based systems are widely used in modern technology environments. In my day-to-day DevOps activities, I regularly work with Linux commands to manage files, monitor processes, troubleshoot services, investigate network problems, analyze logs, and resolve production issues. This guide covers essential Linux administration concepts and commands that are useful for DevOps engineers, along with practical examples of how they can be applied during everyday troubleshooting. 1. Understanding Linux File Permissions Linux uses a permission system to control access to files and directories. The three basic permissions are: Read (r) – Allows a user to view the contents of a file or directory. Write (w) – Allows modifications to a file or directory. Execute (x) – Allows a file to be executed or a director...